Versions:

  • 0.3.2

wmux is a terminal session persistence utility for Windows, published by HomeOps and currently at version 0.3.2, which is the only version listed in the catalog. Its purpose is narrow and deliberate: it keeps a console session alive after the window hosting it closes, filling a gap in the Windows terminal ecosystem. A user starts a session, detaches with the Ctrl-B d key sequence, closes the terminal window, and later reattaches to find the shell and every process running inside it fully intact. The tool belongs to the terminal and console utilities category, but unlike full terminal multiplexers it is deliberately scoped to session persistence alone, offering no panes, no splits, and no status bar. The design rationale is that Windows Terminal already supplies tabs, splits, and search, so wmux handles the one capability Windows lacks—detached, persistent sessions—and leaves display features to the terminal application itself. Technically, wmux is built directly on ConPTY, the Windows pseudoconsole infrastructure. A detached server process owns the pseudoconsole and holds no console of its own, which means the close event delivered to the window that launched the session never reaches the session itself, allowing it to survive window closure. Use cases include keeping long-running builds, scripts, or interactive shells alive across accidental or intentional window closures, and returning to exactly the same working state at a later time. In addition to interactive use, wmux supports automation: scripts can drive a session without any terminal attached at all, making it suitable for headless or scripted workflows where a persistent console process is needed without a visible window. With a single published version so far, wmux represents an early-stage, focused complement to Windows Terminal rather than a replacement for it, targeting users who want tmux-style session survival without the additional multiplexing features.

Tags: